fix(component-manager): route fw update requests through the host reprovisioning flow for non rack-scale systems#2439
Conversation
…rovisioning flow for non rack-scale systems. Continue using the rack-level maintenanance flow to upgrade rack-scale systems (only GB200 today)
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
zhaozhongn
left a comment
There was a problem hiding this comment.
Does this mean rack compute tray will always go to RMS state path? If RMS is not configured as backend for compute, should those still go through the non-rack path?
Description
fix(component-manager): route fw update requests through the host reprovisioning flow for non rack-scale systems. Continue using the rack-level maintenanance flow to upgrade rack-scale systems (only GB200 today)
Type of Change
Related Issues (Optional)
Breaking Changes
Testing
Additional Notes